[Entity Analytics] [8.18 Only] Add deprecation warning for the legacy risk score modules #202775
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
hop-dev
added
Team: SecuritySolution
|
Pinging @elastic/security-solution (Team: SecuritySolution) |
|
Pinging @elastic/security-entity-analytics (Team:Entity Analytics) |
hop-dev
added
ci:project-deploy-security
hop-dev
changed the title
hop-dev
added
ci:cloud-deploy
|
@elasticmachine merge upstream |
|
@elasticmachine merge upstream |
x-pack/plugins/security_solution/server/deprecations/register_risk_score_modules_deprecation.ts
Outdated
Show resolved
Hide resolved
x-pack/plugins/security_solution/server/deprecations/register_risk_score_modules_deprecation.ts
Outdated
Show resolved
Hide resolved
x-pack/plugins/security_solution/server/deprecations/register_risk_score_modules_deprecation.ts
Outdated
Show resolved
Hide resolved
x-pack/plugins/security_solution/server/deprecations/register_risk_score_modules_deprecation.ts
Outdated
Show resolved
Hide resolved
…risk_score_modules_deprecation.ts Co-authored-by: natasha-moore-elastic <137783811+natasha-moore-elastic@users.noreply.github.com>
…risk_score_modules_deprecation.ts Co-authored-by: natasha-moore-elastic <137783811+natasha-moore-elastic@users.noreply.github.com>
…risk_score_modules_deprecation.ts Co-authored-by: natasha-moore-elastic <137783811+natasha-moore-elastic@users.noreply.github.com>
|
/ci |
|
/ci |
|
@elasticmachine merge upstream |
|
/ci |
…na into deprecate-risk-score-module
lcawl
approved these changes
Dec 13, 2024
Co-authored-by: Lisa Cawley <lcawley@elastic.co>
Co-authored-by: Lisa Cawley <lcawley@elastic.co>
|
@elasticmachine merge upstream |
💚 Build Succeeded
Metrics [docs]Async chunks
Page load bundle
History
cc @hop-dev |
natasha-moore-elastic
approved these changes
Dec 17, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Note
Example deployment with data loaded (message me for credentials): https://kibana-pr-202775.kb.us-west2.gcp.elastic-cloud.com/app/management/stack/upgrade_assistant/kibana_deprecations
Add a deprecation warning when users have the risk scoring modules/legacy risk engine installed.
We are removing the legacy risk engine in 9.0.0 which means users data will be there in the index but the UI won’t display it, scores will even continue to be calculated if they for some reason don’t upgrade to the new risk engine. But there will be no dedicated views in kibana.
In 8.18 we are adding an upgrade assistant warning if they have the legacy risk engine installed, this is to guide them to upgrade.
I have tried to use the same language as our documentation by calling it the risk score module.
Upgrade Assistant List view:
Clicking the deprecation:
Test Steps
yarn start generate-legacy-risk-scorecommand.